Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 580-tree-1
name: 1499
tree-preservation-order: undefined
580-tpo-1
uprn
address-text
point: POINT (-0.971223 50.867078)
geometry: MULTIPOLYGON (((-0.971124 50.867067,-0.971128 50.867087,-0.971142 50.867104,-0.971163 50.867118,-0.971191 50.867128,-0.971222 50.867131,-0.971252 50.867128,-0.971280 50.867119,-0.971303 50.867106,-0.971317 50.867088,-0.971322 50.867069,-0.971318 50.867049,-0.971304 50.867032,-0.971283 50.867018,-0.971255 50.867008,-0.971224 50.867005,-0.971194 50.867008,-0.971166 50.867017,-0.971143 50.867030,-0.971129 50.867048,-0.971124 50.867067)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL